Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-76849 | IISW-SI-000241 | SV-91545r2_rule | Medium |
Description |
---|
The use of a DoD PKI certificate ensures clients the private website they are connecting to is legitimate, and is an essential part of the DoD defense-in-depth strategy. |
STIG | Date |
---|---|
IIS 8.5 Site Security Technical Implementation Guide | 2019-03-20 |
Check Text ( C-76505r1_chk ) |
---|
Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. Click the site name under review. Click “Bindings” in the “Action” Pane. Click the “HTTPS type” from the box. Click “Edit”. Click “View” and then review and verify the certificate path. If the list of CAs in the trust hierarchy does not lead to the DoD PKI Root CA, DoD-approved external certificate authority (ECA), or DoD-approved external partner, this is a finding. If HTTPS is not an available type under site bindings, this is a finding. |
Fix Text (F-83545r1_fix) |
---|
Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. Click the Server name. Double-click “Server Certificates”. Click “Import” under the "Actions" pane. Browse to the DoD certificate location, select it, and click “OK”. Remove any non-DoD certificates if present. Click on the site needing the certificate. Select “Bindings” under the "Actions" pane. Click on the binding needing a certificate and select “Edit”, or add a site binding for HTTPS. Assign the certificate to the website by choosing it under the “SSL Certificate” drop-down and clicking “OK”. |